Introduce Randomized Batch Sizes in Batch Utilities for Property Testing

This PR updates the batch utility logic to split input data into batches of random sizes (rather than consistently sized slices) for testing whether variable batch sizes impact downstream processing. The batching function is modified to use a random size (within the allowed maximum) during the batch split process, aligning with the stated intent to evaluate robustness against non-uniform batches.

Key Changes:
• Adds 'import random' to support randomized batch sizes.
• Modifies 'create_batches' to generate batches of random sizes between 1 and the API's max batch size when splitting input greater than the maximum.
• Removes old logic for fixed-size batching.

Affected Areas:
• chromadb/utils/batch_utils.py

This summary was automatically generated by @propel-code-bot

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Do not merge this as it breaks the client batching lib.